Stack processor using a ferroelectric random access memory (F-RAM) for code space and a portion of the stack memory space having an instruction set optimized to minimize processor stack accesses

ABSTRACT

A stack processor and method implemented using a ferroelectric random access memory (F-RAM) for code and a portion of the stack memory space having an instruction set optimized to minimize processor stack accesses and thus minimize program execution time. This is particularly advantageous in low power applications and those in which the power supply is only available for a finite period of time such as RFID implementations. Disclosed herein is a relatively small but complete set of instructions enabling a multitude of possible applications to be supported with a program execution time that is not too long.

RELATED APPLICATION

The present invention claims priority from U.S. Provisional Application No. 61/486,652, filed May 16, 2011, and is related to U.S. patent application Ser. No. 13/467,831 “Stack Processor Using a Ferroelectric Random Access Memory (F-RAM) for Both Code and Data Space”; Ser. No. 13/467,849 for “Stack Processor Using a Ferroelectric Random Access Memory (F-RAM) for Code Space and a Portion of the Stack Memory Space”; and Ser. No. 13/467,816 for “Stack Processor Using a Ferroelectric Random Access Memory (F-RAM) Having an Instruction Set Optimized to Minimize Memory Fetch Operations” all filed on even date herewith. The disclosures of the aforementioned applications are herein specifically incorporated by reference in their entirety.

BACKGROUND OF THE INVENTION

The present invention relates, in general, to the field of customizable integrated circuit devices incorporating non-volatile memory. More particularly, the present invention relates to a stack processor and method implemented using a ferroelectric random access memory (F-RAM) for code and a portion of the stack memory space having an instruction set optimized to minimize processor stack accesses.

Current nonvolatile memory technologies include, among others, electrically erasable programmable read only memory (EEPROM) and Flash memory. Despite continuing improvements to this technology, the endurance rate of Flash memory is still multiple orders of magnitude below the endurance rate of F-RAM. Therefore, for applications using Flash memory that require high endurance, some products will actually include a large Flash memory array with the associated user/program ensuring that data is stored in specific memory locations (e.g. banks of memory). Once a memory bank approaches its endurance limit, the user/program would then enable the movement of all data to a new memory bank, marking the previous memory bank as worn out and indicating it should not be used again. The typical endurance of such floating gate devices is approximately between 100,000 to 1 million write cycles.

It is also well known that writes to EEPROM and Flash is relatively slow compared to that of F-RAM. While a F-RAM write cycle is completed almost immediately, EEPROM and Flash write times take meaningfully longer. Still further, writes to an F-RAM memory cell occur at a relatively low voltage and very little current is required to change the data in the cell.

A currently implemented architecture for a stack processor is the b16 Processor described in Paysan, B., “A Forth Processor in an FPGA”, Feb. 2, 2003; Paysan, B., “b16—small—Less is More”, Jul. 9, 2006; and Paysan, B., “b16: Modern Processor Core”, Apr. 29, 2005 and disclosed at http://www.jwdt.com/˜paysan/b16.html. The b16 stack based processor has the top of the stacks maintained in volatile registers and the bottom of the stacks in two complementary metal oxide semiconductor (CMOS) memories. Such an architecture will lead to the possibility of the data and return stacks and code space being accessed simultaneously. Moreover, a stack processor architecture which provides for maintaining the stacks in volatile memory would cause it to suffer from very long and power demanding power-down times as the contents of a relatively large number of registers would have to be saved to nonvolatile memory on power-down. Placing some of the registers in nonvolatile Flash memory in an attempt to ameliorate this situation would, of course, lead to the endurance issues inherent in Flash. Still further, a stack processor architecture which utilizes a different memory type for code and the stacks would suffer from high power consumption peaks since all of the memories are likely to be accessed simultaneously in normal operation.

In the b16 stack processor, each 16 bit word is mapped as three, 5 bit instructions and one extra 1 bit instruction which can only be a “no operation” (NOP) or CALL. In practice this means that in the majority of cases, the fourth instruction will generally be a NOP and the instruction set is, therefore, wasting one bit per word along with a clock cycle (needed to execute the NOP) every three instructions. Still further, the b16 stack processor does not share code and data space so its architecture is even more power demanding as it can access code space and the data and return stacks all simultaneously.

SUMMARY OF THE INVENTION

Customizable integrated circuit devices will generally require the provision of some sort of processing unit on-chip to enable the device to execute different functions depending on a user defined program. One example market for customizable devices is in the field of metering functions which require higher endurance cycles than can reasonably be supplied by nonvolatile memory technologies such as Flash. Another possible market is radio frequency identification (RFID) in which low power memory cells are required.

Currently many companies also intend to develop products that operate in an environment where power supply voltage can, at times, be lost. In such applications, a need exists to be able to save current data quickly into non-volatile storage before power-down occurs.

To this end, a need also exists for an integrated circuit architecture that embodies a processor in conjunction with associated F-RAM memory. As power-down time in the event of a supply voltage disruption should be as quick as possible, it is advantageous to have as much data as possible in non-volatile memory. Stack based processors are particularly useful in such an application inasmuch as most of the registers it manipulates are in the stack.

Therefore, in using a stack-based processor, if some or all of the stacks are in F-RAM memory, most of the data is already in non-volatile memory at any given time. Even if some of the data is not already stored in F-RAM memory, the very fast write time of that memory technology also allows for the rapid back-up of the data. Moreover, such an architecture can be readily customized through the changing of the processor program allowing a wide range of potential applications such as metering functions, RFID and the like. Further, inherent in the operation of F-RAM memory is its low leakage and dynamic power requirements. The architecture disclosed herein also results in less routing congestion as there is only one code/data bus employed and it communicates with only one memory in a particular embodiment of the present invention.

In a particular embodiment of the architecture of the present invention disclosed herein the stack-based processor has all of its stacks stored in F-RAM memory. This presents the advantages of easy stack pointer management inasmuch as the stack pointer is itself a memory address. The time for saving all critical registers to memory is also minimized in that all registers are already maintained in non-volatile F-RAM per se. As previously mentioned the fast write times and low power access inherent in F-RAM provide many advantages while the use of a single, unique memory type on-chip affords easier hardware management, less intellectual property (IP) costs and also results in a smaller on-chip die area.

In accordance with another particular embodiment of the architecture of the present invention disclosed herein the stack-based processor has some, but not all, of its stacks stored in non-volatile F-RAM memory and the remainder in volatile memory. By storing some of the associated stacks in complementary metal oxide semiconductor (CMOS) or other volatile memory, read/write operations to only F-RAM would be obviated. Even though F-RAM memory requires relatively low power compared to other non-volatile memory technologies, an access to volatile memory instead could provide at least some power advantages. Further, read/write accesses to F-RAM memory only can somewhat slow down program execution and being able to access the stack memories in parallel to code execution would result in certain speed advantages. This is particularly relevant to RFID applications wherein power is only available for a relatively short, finite time when the card enters the RF field of the associated controller.

Implementing a stack processor with this type of architecture results in a compromise between an all F-RAM memory implementation providing a quicker power-down time, smaller on-chip die area and a relatively slower, more power consuming program execution versus a somewhat longer power-down time, larger on-chip die area, and a faster, less power consuming operation with a faster program execution time. Having the processor stack only partially maintained in F-RAM memory also has the advantage that, if the program compiler makes efficient use of this particular architecture, it can generate firmware code that will tend to concentrate the more intensive calculations to that part of the stack that is in volatile memory and minimize POP/PUSH operations to the F-RAM portion of the stack. Such an application will result in faster program execution through parallel access to the volatile registers which also consume less power than F-RAM memory. Moreover, since only the top of the stack is in volatile memory, most of it remains in F-RAM which means the application can still benefit from the high F-RAM endurance and shorter power-down times.

In accordance with yet another embodiment of the architecture of the present invention disclosed herein is a particular processor implementation utilizing an instruction set optimized to minimize memory fetches and thus minimize program execution time. This provides a number of distinct advantages including various low power applications and those in which the power supply is only available for a finite period of time such as RFID implementations. The use of a processor with such an optimized instruction set also allows the architecture of the present invention to be instantiated across multiple devices to support a wide range of possible operations and differing numbers of peripherals by supporting interrupts as will be more fully described hereinafter.

This particular embodiment of the present invention provides an instruction set for a stack processor architecture that is relatively small so that the associated logic is itself not too large thereby reducing current leakage and dynamic power requirements. Also disclosed is a complete set of instructions so that a multitude of possible applications can be supported with a program execution time that is not too long. Further, the instruction set disclosed is neither too complex nor too light. That is, there are not too many F-RAM memory fetches and nor is there too much logic leakage. As disclosed, the instruction set of the present invention supports the basic Forth commands as well as other operation code for generic operations while also supporting interrupts.

In accordance with still another embodiment of the architecture of the present invention disclosed herein is a particular method of operation which minimizes processor stack accesses when the associated stack is only partially implemented in F-RAM memory. The minimization of F-RAM stack accesses in conjunction with the particular processor described and disclosed herein results in less power being consumed as well as overall faster program execution as would be the case were all of the stack held in non-volatile F-RAM memory, in which instance the code could not be read while accessing the F-RAM stack.

Specifically disclosed herein is a method for operating a stack processor in an integrated circuit device which comprises coupling a non-volatile memory to the stack processor for storing program code and at least a portion of the stack memory space and also coupling a volatile memory to the stack processor for storing another portion of the stack memory space. The stack memory space comprises data and return stacks and the bottom portions of the data and return stacks are maintained in the non-volatile memory and the top portions are maintained in the volatile memory.

BRIEF DESCRIPTION OF THE DRAWINGS

The aforementioned and other features and objects of the present invention and the manner of attaining them will become more apparent and the invention itself will be best understood by reference to the following description of a preferred embodiment taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a functional block diagram of a stack processor using a ferroelectric random access memory (F-RAM) for both code and data space in accordance with a particular representative embodiment of the present invention;

FIG. 2 is a follow-on functional block diagram of a portion of a stack processor utilizing both F-RAM and CMOS memory in accordance with another particular representative embodiment of the present invention;

FIGS. 3A through 3D inclusive are exemplary illustrations of an instruction for the copying of the top of the data. stack (“T”) into the top of a return stack (“R”);

FIG. 4 is an exemplary illustration of a method in accordance with the representative embodiment of the present invention illustrated in FIG. 2 wherein the CMOS registers are only updated when required and unused portions of the CMOS stack are not updated to conserve power;

FIG. 5 is an exemplary illustration of a 16 bit instruction set in accordance with a particular embodiment of the present invention which has been optimized to minimize memory fetches; and

FIG. 6 is an exemplary table of possible operating code mappings for the Forth core of the preceding FIGS. 1 and 2.

DESCRIPTION OF A REPRESENTATIVE EMBODIMENT

With reference now to FIG. 1, a functional block diagram of a stack processor 100 using a ferroelectric random access memory (F-RAM) for both code and data space in accordance with a particular representative embodiment of the present invention is shown. The stack processor 100 comprises, in pertinent part, a F-RAM memory array 102 and associated processor 104. The F-RAM memory array 102 may be of the type provided by Ramtron International Corporation, Colorado Springs, Colo., assignee of the present invention. The processor 104, as shown, may comprise a Forth core 106 developed by Ramtron International Corporation, assignee of the present invention.

An associated interrupt controller 108 forms a portion of the processor 104 which also operates in conjunction with a clock reset circuit 110 as shown. In the representative embodiment illustrated, eight modules (Module 1 through Module 8) respectively labeled as 112 ₁ through 112 ₈ inclusive are associated with the stack processor 100. A single code/data bus couples the Forth core 106 to the F-RAM memory array 102 and comprises memory read and write lines (mem_rd, mem_wr) and 16 bit memory address, memory write data and memory read data buses (mem_address, mem_wr_data, mem_rd_data) buses as illustrated.

The clock reset circuit 110 provides a clock interrupt signal (clk_int) to the interrupt controller 108 as well as a reset n (rst_n) signal to both the Forth core 106 and interrupt controller 108. The clock reset circuit 110 also provides a core clock signal (clk_core) to the Forth Core 106 and receives a core_need_clock therefrom. The interrupt controller 108 provides an interrupt signal (int) and a 3 bit int_nb signal to the Forth core 106 and receives an interrupt clear (int_clr) and ongoing interrupt (int_ongoing) signals therefrom.

With reference additionally now to FIG. 2, a follow-on functional block diagram of a portion of a stack processor 200 utilizing both F-RAM and CMOS memory in accordance with another particular representative embodiment of the present invention is shown. As indicated, there is only one processor code/data bus, and it goes to the F-RAM memory array 202 only. The stack processor 200 comprises a Forth Core 204 having a data stack 210 and a return stack 212 while the F-RAM memory array 202 has a corresponding data stack bottom 206 and a return stack bottom 208.

In this figure the organization of an embodiment of the stack processor 200 is shown. The data stack 210 has its top part in the processor core 204 in volatile CMOS registers in this case. The bottom of the data stack 206 is in the nonvolatile F-RAM memory array 202. In the same manner, the top of the return stack 212 is in the processor core 204 in volatile CMOS registers 212 and the bottom of the return stack 208 is in the F-RAM memory array 202. Therefore, if a program only needs to modify the top of the data stack with no push/pop to the F-RAM memory array 202 stack, only CMOS register accesses will be involved. This would result in overall lower power consumption. If a power down were to occur, there would then only be the contents of a very limited number of CMOS registers to save before a power loss occurs.

It should be noted that a portion of the performance of this particular stack processor 200 implementation is due to the instruction set. However, some of it also results from the fact that the program is relatively small and can be written to derive benefit from the top of the stacks being in CMOS registers.

With reference additionally now to FIGS. 3A through 3D inclusive, exemplary illustrations of an instruction for the copying of the top of the data stack (“T”) into the top of a return stack (“R”) are shown.

The proposed stack access method illustrated maintains track of the where the stack pointer is relative to the boundary between the CMOS and F-RAM portions of the stack. As illustrated, a data transfer between the data and return stacks can result in four possible initial configurations. The shaded boxes indicate that there is valid data in this stack memory address.

In FIG. 3A, the data AND return stack have not passed the F-RAM boundary. In FIG. 3B, the data stack ONLY has passed the F-RAM boundary. In FIG. 3C, the return stack ONLY have passed the F-RAM boundary and in FIG. 3D, both the data and return stack have passed the F-RAM boundary

As can be seen, according to the specific configuration, the proposed algorithm performs or does not perform a stack pop/push and for the specific instruction outlined above, the algorithm would do the following:

As shown in FIG. 3A, copy T into R; as shown in FIG. 3B, POP the data stack and copy T into R; as shown in FIG. 3C, PUSH the return stack and copy T into R; and as shown in FIG. 3D, PUSH the return stack, POP the data stack and copy T into R. In this manner, only a minimum number of F-RAM memory array accesses are required.

With reference additionally now to FIG. 4, an exemplary illustration of a method in accordance with the representative embodiment of the present invention illustrated in FIG. 2 is shown wherein the CMOS registers are only updated when required and unused portions of the CMOS stack are not updated to conserve power. In this implementation of the present invention, the third CMOS register bus of the stack has not been updated or reset and since it is now in the unused part of the stack its current value is “don't care”. As can be determined, not updating that register bus allows for the saving of some more power.

With reference additionally now to FIG. 5, an exemplary illustration of a 16 bit instruction set in accordance with a particular embodiment of the present invention is shown which has been optimized to minimize memory fetches.

In this particular implementation of the present invention, the disclosed instruction set is based on a 16 bit memory code space. In order to determine the appropriate instruction set, the following possibilities may be examined:

-   -   any 4 bit instruction (or less) set would allow up to 16         instructions (or less) and so would not be sufficient as the         program would take too long to execute with too many F-RAM         memory array fetches;     -   any 7 bit instruction set (or more) would require 128         instructions or more, so too much leakage/dynamic power would be         required and the logic would be excessively large;     -   a 6 bit instruction set would require 64 instructions, which         while sufficient, is nonetheless very difficult to map into a         16-bit word without wasting too many bits;     -   a 5 bit instruction set would require 32 instructions and would         appear to be a bit too limiting.

As can be seen in the exemplary instruction set illustrated, 64 instructions can be provided while minimizing the waste of memory bits. The 16 bit word MSB is a bit used by each instruction, therefore each instruction is 6 bits wide (which gives a total of 64 instructions maximum). As a consequence, the full 16 bits of code are used.

With reference additionally now to FIG. 6, an exemplary table of possible operating code (“opcode”) mappings for the Forth core of the preceding FIGS. 1 and 2 is shown. As illustrated, the Forth core instructions are grouped by the categories of: Branching, Memory Access, Logic, Arithmetic and Data Stack and those opcodes are shown which share the same five lower significant bits and differ only by the one most significant group bit as shown in the preceding FIG. 5.

While there have been described above the principles of the present invention in conjunction with specific circuitry and technology, it is to be clearly understood that the foregoing description is made only by way of example and not as a limitation to the scope of the invention. Particularly, it is recognized that the teachings of the foregoing disclosure will suggest other modifications to those persons skilled in the relevant art. Such modifications may involve other features which are already known per se and which may be used instead of or in addition to features already described herein. Although claims have been formulated in this application to particular combinations of features, it should be understood that the scope of the disclosure herein also includes any novel feature or any novel combination of features disclosed either explicitly or implicitly or any generalization or modification thereof which would be apparent to persons skilled in the relevant art, whether or not such relates to the same invention as presently claimed in any claim and whether or not it mitigates any or all of the same technical problems as confronted by the present invention. The applicants hereby reserve the right to formulate new claims to such features and/or combinations of such features during the prosecution of the present application or of any further application derived therefrom.

As used herein, the terms “comprises”, “comprising”, or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a recitation of certain elements does not necessarily include only those elements but may include other elements not expressly recited or inherent to such process, method, article or apparatus. None of the description in the present application should be read as implying that any particular element, step, or function is an essential element which must be included in the claim scope and THE SCOPE OF THE PATENTED SUBJECT MATTER IS DEFINED ONLY BY THE CLAIMS AS ALLOWED. Moreover, none of the appended claims are intended to invoke paragraph six of 35 U.S.C. Sect. 112 unless the exact phrase “means for” is employed and is followed by a participle. 

What is claimed is:
 1. A method for operating a stack processor comprising: a data POP wherein data is transferred from a bottom portion of a data stack to a top portion of the data stack in a first cycle of the stack processor, wherein the top portion of the data stack is in a volatile memory in a Forth core in the stack processor and the bottom portion of the data stack is in a ferroelectric random access memory in the stack processor, separate from the Forth core and coupled to the Forth core by a single code/data bus extending between the Forth core and ferroelectric random access memory only, and wherein data is transferred from the bottom portion of the data stack to the top portion of the data stack through the single code/data bus; transferring data from the top portion of the data stack to a top portion of a return stack in a second cycle of the stack processor, wherein the top portion of the return stack is a single register in the volatile memory, and wherein transferring data between the top portion of the data stack and the top portion of the return stack comprises copying data in the top portion of the data stack to the top portion of the return stack; and a return PUSH wherein data is transferred from the top portion of the return stack to a bottom portion of the return stack in a third cycle of the stack processor, wherein the bottom portion of the return stack is in the ferroelectric random access memory, and wherein data is transferred from the top portion of the return stack to the bottom portion of the return stack through the single code/data bus, wherein the first, second and third clock cycles are sequential, and wherein the data POP, return PUSH and the transferring data are performed in response to a stack-based computer programming language.
 2. The method of claim 1 wherein the stack-based computer programming language comprises 64 possible instructions based upon a 16 bit word, wherein each of the instructions in the 16 bit word comprises 3 five bit instructions and a 16^(th) bit applicable to each of the 3 five bit instructions.
 3. A method for operating a stack processor comprising: in a first cycle of the stack processor transferring data from a bottom portion of a data stack to a top portion of the data stack, wherein the bottom portion of the data stack is in a ferroelectric random access memory (F-RAM) and the top portion of the data stack is in a volatile memory in a Forth core in the stack processor, and the data is transferred through a single code/data bus coupled between the F-RAM and the Forth core only; in a second cycle of the stack processor copying the data from the top portion of the data stack to a top portion of a return stack, wherein the top portion of the return stack comprises a single register in the volatile memory; and in a third cycle of the stack processor transferring the data from the top portion of the return stack to a bottom portion of the return stack, wherein the bottom portion of the return stack is in F-RAM and the data is transferred through the single code/data bus.
 4. The method of claim 3 wherein the transferring and the copying of data are performed in response to a stack-based computer programming language supporting Forth core instructions.
 5. The method of claim 4 wherein the Forth core instructions comprise 64 possible instructions based upon a 16 bit word, wherein each of the instructions in the 16 bit word comprises 3 five bit instructions and a 16th bit applicable to each of the 3 five bit instructions.
 6. A method for operating a stack processor comprising: transferring data from a bottom portion of a data stack to a top portion of the data stack, wherein the bottom portion of the data stack is in a ferroelectric random access memory (F-RAM) and the top portion of the data stack is in a volatile memory in a Forth core in the stack processor and the data is transferred through a single code/data bus coupled between the F-RAM and the Forth core only; copying data from the top portion of the data stack to a top portion of a return stack, wherein the top portion of the return stack comprises a single register in the volatile memory; and transferring the data from the top portion of the return stack to a bottom portion of the return stack, wherein the bottom portion of the return stack is in F-RAM and the data is transferred through the single code/data bus, wherein the transferring and the copying of data are performed in three sequential clock cycles of the stack processor in response to Forth core instructions.
 7. The method of claim 6 wherein the Forth core instructions comprise 64 possible instructions based upon a 16 bit word, wherein each of the instructions in the 16 bit word comprises 3 five bit instructions and a 16th bit applicable to each of the 3 five bit instructions. 